TPVM Upgrade Workflow

About this task

Follow this TPVM upgrade procedure to upgrade an existing TPVM.

1. Perform validations on user input for the device IP, firmware host, and TPVM image.
   1. The device IP is a registered device with the minimum supported SLX version and with the associated TPVM configuration. It must be one of the XCO HA peers managing the device.
   2. Ensure that the firmware host is registered prior to TPVM upgrade.
   3. The TPVM image is validated during the SLX TPVM upgrade.
2. Read the current TPVM configuration and operational data (including TPVM version and IP address) from the device, and then perform the following validations. TPVM configuration is pushed to the device in the node replacement case.
   1. If TPVM is neither configured nor installed, then the TPVM configuration existed in the XCO DB is pushed to the device, and TPVM instance is installed. This operation supports the node replacement RMA case.
   2. If TPVM configuration from the device differs from the existing XCO configuration, then the device‘s configuration has priority, and the XCO DB is updated.
   3. When you set the TPVM configuration interface management IP to DHCP, ensure that the TPVM IP address remains the same. This is due to a dependency on XCO deployment where a peer node is configured with a specific IP address in the active node. You cannot change the peer node IP without restarting XCO HA cluster daemons on an active node.
   TPVM Configuration Special Handling for All Cases

   • You must re-apply the trusted-peer configuration on the node where it was already applied. It exists on only one of the nodes in the XCO HA cluster. An appropriate node is identified and the trusted peer configuration is pushed to the correct node during TPVM upgrade or node replacement.
3. Run an appropriate SLX command on the device to upgrade or install the TPVM.
   1. Run the tpvm upgrade command on the device. The device stops and takes a snapshot to roll back in case of failure. The device downloads the TPVM image and upgrade the TPVM instance. The TPVM starts after the upgrade, and the existing TPVM configurations are programmed on the running TPVM instance.
   2. During node replacement, the TPVM configuration is pushed to the device, and the tpvm deploy command is run on the device. You do not require a TPVM snapshot because the replacement switch is a new switch without a configured TPVM.
4. Redeploy XCO on the upgraded or installed TPVM node from the active node. Allow the redeployed peer node to rejoin the XCO HA cluster.

Example

The following example shows an output of TPVM upgrade execute command:

(efa:extreme)extreme@node-1:~$  efa inventory device tpvm-upgrade execute --ip 10.20.48.162 --firmware-host 10.31.2.101  \
>  --tpvm-image /buildsjc/sre_fusion/Nightly/tpvm/tpvm4.5.6/tpvm4.5.6_221103_2338/dist/SWBD2900/tpvm-4.5.6-0.amd64.deb
TPVM Upgrade Execute [success]
Monitor TPVM upgrade execution progress using:

  efa inventory device tpvm-upgrade show --ip 10.20.48.162
  efa inventory device tpvm-upgrade show --execution-id a2c07243-bae0-46ea-aa2c-e932e409d0bd

Please do not execute other commands on the device until process is completed

--- Time Elapsed: 145.914563ms ---
(efa:extreme)extreme@node-1:~$ while [ 1 ] ; do efa inventory device tpvm-upgrade show --ip 10.20.48.162 ; sleep 120s ; done
+--------+----+-----+--------+-----+------+-------------+-----------+--------+-----------------+----------+-------+------------+------------------+------------------+
|IP      |Host|Model|Chassis | ASN | Role | Current TPVM|Target TPVM|Update  |       Status    | Detailed | Failed|   Upgrade  |    Start Time    | Last Update Time |
|Address |Name|     |Name    |     |      | Version     |Version    |State   |                 | Status   | State |   Type     |                  |                  |
+--------+----+-----+--------+-----+------+-------------+-----------+--------+-----------------+----------+-------+------------+------------------+------------------+
|10.20   |AS2 |3012 |SLX9250 |64512| Spine| 4.5.3       |           |In      |Device Validation| None     |       |Incremental |2022-11-05        |2022-11-05        |
|.48.162 |    |     |-32C    |     |      |             |           |Progress|    Started      |          |       |Upgrade     |23:52:29 -0700 PDT|23:52:36 -0700 PDT|
+--------+----+-----+--------+-----+------+-------------+-----------+--------+-----------------+----------+-------+------------+------------------+------------------+
TPVM Upgrade Show Details
--- Time Elapsed: 372.428607ms ---

+-------+----+-----+-------+-----+-----+-----------+------------+---------+-------------------+-----------------+------+------------+------------------+------------------+
|IP     |Host|Model|Chassis|ASN  |Role |Current    |Target TPVM |Update   |       Status      |    Detailed     |Failed|  Upgrade   |    Start Time    | Last Update Time |
|Address|Name|     |Name   |     |     |TPM Version|Version     |State    |                   |    Status       |State |  Type      |                  |                  |
+-------+----+-----+-------+-----+-----+-----------+------------+---------+-------------------+-----------------+------+------------+------------------+------------------+
|10.20  |AS2 |3012 |SLX9250|64512|Spine|   4.5.6   |   4.5.6    |Completed| TPVM Upgrade      |Reboot Required  |      |Incremental |2022-11-05        |2022-11-06        |
|.48.162|    |     |-32C   |     |     |           |            |         | Workflow Completed|for TPVM Instance|      |Upgrade     |23:52:29 -0700 PDT|00:01:11 -0700 PDT|
+-------+----+-----+-------+-----+-----+-----------+------------+---------+-------------------+-----------------+------+------------+------------------+------------------+